You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This feels a little mixed up: ref and numref don't specify the target type, it may be a header, figure, table, etc. On the other hand eq and doc specify the target type (but don't differentiate between reference or numbered reference).
Should these kinds be specific in their target type? mathtablefigure etc? Or should they simply be references to be resolved later? There are pros/cons each way - e.g. the former requires more validation but allows knowledge of the target type without resolving the reference every time.
This is quite limited in the spec to:
eq
,numref
,ref
,doc
https://github.com/executablebooks/myst-spec/blob/main/schema/references.schema.json#L37 (even doc is missing in this schema file) - this matches the jupyterbook myst documentation https://jupyterbook.org/content/references.html#reference-figuresThis feels a little mixed up:
ref
andnumref
don't specify the target type, it may be a header, figure, table, etc. On the other handeq
anddoc
specify the target type (but don't differentiate between reference or numbered reference).Should these kinds be specific in their target type?
math
table
figure
etc? Or should they simply bereferences
to be resolved later? There are pros/cons each way - e.g. the former requires more validation but allows knowledge of the target type without resolving the reference every time.We can also introduce kind + domain, like sphinx does here: https://www.sphinx-doc.org/en/master/usage/restructuredtext/domains.html#the-math-domain
The text was updated successfully, but these errors were encountered: