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
It seems it was attempted to make a code highlight in details/accordion heading here for ReplaceNestedContentDataTypeArtifactMigrator.cs and NestedContentPropertyTypeMigrator.cs ... I guess GitBook just handle these as raw text eventually. Perhaps we should just remove the quotes if not supported here?
The text was updated successfully, but these errors were encountered:
Hi @bjarnef thank you for bringing this to our attention 🙏
Gitbook had a recent update on their platform which seems to have affected parts of our content such as the one you have noticed. It seems that in the dropdowns, instead of using quotes ' for code, they have changed the format for code to use code tags instead:
I will bring this up with the Gitbook support to see if we can do something about this and if not, then we might need to manually change all dropdowns from the whole documentation to fit with the new code syntax😅
Hi @bjarnef ! 👋
I'm going through our Issue Tracker to get things cleaned up for the upcoming Hacktoberfest months.
Noticed this one, and was wondering whether it's still relevant?
I'm unable to find any issues with the dropdowns (or expendables as the block is called in GitBook) - but I might be looking the wrong place? 🤔
What type of issue is it? (Choose one - delete the others)
Discussion
Other (visually bug in docs)
What article/section is this about?
https://docs.umbraco.com/umbraco-deploy/v/12.deploy.latest/deployment-workflow/import-export#migrating-whilst-importing
Describe the issue
It seems it was attempted to make a code highlight in details/accordion heading here for
ReplaceNestedContentDataTypeArtifactMigrator.cs
andNestedContentPropertyTypeMigrator.cs
... I guess GitBook just handle these as raw text eventually. Perhaps we should just remove the quotes if not supported here?The text was updated successfully, but these errors were encountered: