techfg

Results 61 comments of techfg

@hippotastic - I was able to figure out why `plugin-frames` and `plugin-text-markers` had a small footprint with the initial proposed `Core` layer introduced in this PR. In short, both of...

@utarwyn - First off, thanks for your work on this plugin, greatly appreciated! Regarding `go.work`, agreed that it should not be included in `sharedGlobals` as it will affect any project...

Awesome to see this merged! Thank you @Julien-Marcou for all your efforts and persistence in getting this through, really appreciate it!

Ran into this requirement today, would be great to see these implemented, ty!

Hi @SnowDingo - Thanks for reviewing this and I agree, I believe the 2nd option is likely best since favicon can be absolute or relative url and therefore I feel...

Hi @SnowDingo - Yes, agreed, not sure which option here is best and why I think waiting for a maintainer to provide input & a decision makes sense before doing...

@SnowDingo - Yes, as mentioned, I would strongly encourage you to wait on any further PR updates until a maintainer has provided guidance on how absolute URLs should be handled....

Hello @SnowDingo - I appreciate your enthusiasm to provide a PR with a fix 😄 However, we still do not know what the starlight maintainers believe the expected behavior should...

Thanks for the update @SnowDingo! @delucis - For when you have the time to review this issue, I think what your suggesting is to keep it relaxed meaning to allow...

Hi @delucis - Thanks reviewing and sorry for the confusion here! 1. #2722 addressed the issue with the [title-wrapper](https://github.com/withastro/starlight/pull/2722/files#diff-aada30a9280a2c888d6ebd674bd53a9405119d82522fef2f95460247f8938662R19) not respecting its flex position within [header](https://github.com/withastro/starlight/pull/2722/files#diff-aada30a9280a2c888d6ebd674bd53a9405119d82522fef2f95460247f8938662R18) and overflowing. 2. This...