BREAKING: Move CrankyTokenFilter to Lucene.Net.Analysis namespace (#1127) #1149
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of the changes
Moved
CrankyTokenFilter
to the correct namespaceLucene.Net.Analysis
.📝 Fixes
Fixes #1127
📚 Description
This pull request addresses issue #1127 by moving
CrankyTokenFilter
from the incorrect namespace:Lucene.Net.TestFramework.Analysis.CrankyTokenFilter
Lucene.Net.Analysis
✅ Details:
CrankyTokenFilter
class to reside in theLucene.Net.Analysis
namespace, aligning it with the correct package as in the original Lucene project (org.apache.lucene.analysis
).Lucene.Net.Analysis.Common
.🧪 Tests
CrankyTokenFilter
have been run successfully.📚 Documentation
🎯 Checklist
🔥 Ready to Merge!
This change ensures that the project structure remains consistent with the original Lucene package, maintaining correctness and improving maintainability.
Thank you for reviewing! 😊🚀