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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Registration API #6246
base: dev/feature
Are you sure you want to change the base?
New Registration API #6246
Changes from 127 commits
1c62976
f913c6b
43d4cee
42fe5ca
3297132
5c69bdc
d74c11f
0fd91f4
98f6b3d
7b5c8b8
c5ac2d0
3e1849f
a44c08e
e467eb0
8b82bb8
501573a
513a008
552e7b5
678cb85
a85016f
11ffcf4
9807e83
f5498a7
2d7f4fb
51782ec
4a00130
3f877f1
04505e0
63957ea
69b5960
5976231
241f97e
eafffac
5b686c0
abab4f7
6cd6215
b9ed60f
7983cf5
db7b807
c983079
8726396
af6c9b7
d768af4
131d07b
e07efe7
0c281fa
78443ff
f4238e9
72049bd
238ab4f
159da8f
130933b
5dbdf41
f402417
3eab3d1
b2a9ef1
db97884
9f912e7
3d6b116
1b9587e
53cba39
61205ea
387b57c
93fe78c
5870190
bab67ee
f376b7b
c67420f
c983968
98a4e1d
30ceb36
f59ae28
6816377
88ecd23
966beb2
3edc884
7ad773f
dc2872b
e763810
7759fcd
eadae09
65ad3a6
bce2323
17937f2
2560021
fc5c637
9c60638
397b831
3f7f973
39f26b2
2316060
bb47855
cc6394f
2ec8806
7dbe48b
97f0603
b025c15
e4a28a0
efaa4fe
eaf5c4e
3333273
6efbb55
3b22fe9
c165765
92712ef
a9c414b
dd7903e
f296812
f272892
a2b9264
a886b25
8998a2e
bd18917
5f483a5
a11a9a9
b97269e
776129e
a7d5088
ce2e82e
e73da23
55fa670
681585c
a0839ef
65507f8
537fc4a
ec1f772
dbc48af
82d1978
036d0b5
2d94cf5
7414f40
6956294
5ffc974
3687940
a15d3cc
f1f4915
96874c5
fd9bb95
b99b686
73a61cd
f4d1df6
f609017
0c30aba
865ddd0
3077f8d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Large diffs are not rendered by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think there should be another method for letting the user specify their own priority for the element?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right now, the methods return the SyntaxInfo that was registered. It would be possible to construct a builder from that SyntaxInfo, change the priority, and then register it again. Of course, having to unregister and then register again is not ideal, but needing to change the priority is not exactly common.
An alternative approach could be to revamp these methods to just return a SyntaxInfo (and then you have to register it yourself), but I'm not sure if that's ideal (and it might conflict with the existing method). What do you think?