BertrandBev / code_field

A customizable code text field supporting syntax highlighting
https://bertrandbev.github.io/code_field/
MIT License
230 stars 61 forks source link

Publish new version to include lineNumbers functionality #67

Closed thekiwi closed 1 year ago

thekiwi commented 1 year ago

First off, great library! Thanks for writing & maintaining it!

I'd like to use the lineNumbers visibility toggle you added into CodeField but I noticed the package published on pub.dev is a little outdated (most recent version was published around a year ago).

Would you be able to publish a new version with the most recent changes?

gumbarros commented 1 year ago

@BertrandBev I also need a new version because of the readOnlyparameter.

t-m-z commented 1 year ago

Also from my side: thank you for your great work. But as thewiki commented - I would like to use the lineNumbers visibility toggle you added into CodeField, too. Thank you in advance.

gumbarros commented 1 year ago

Guys if the mainteiner don't respond, should we fork the project and publish to pub.dev?

t-m-z commented 1 year ago

This would be a proper solution. However until now I have never built a package. I am not such a skilled developer.

regards Thomas

Sent from MailDroid

-----Original Message----- From: Gustavo Mauricio de Barros @.> To: BertrandBev/code_field @.> Cc: Thomas @.>, Comment @.> Sent: So., 16 Okt. 2022 18:02 Subject: Re: [BertrandBev/code_field] Publish new version to include lineNumbers functionality (Issue #67)

Guys if the mainteiner don't respond, should we fork the project and publish to pub.dev?

-- Reply to this email directly or view it on GitHub: https://github.com/BertrandBev/code_field/issues/67#issuecomment-1279998195 You are receiving this because you commented.

Message ID: @.***>

gumbarros commented 1 year ago

I will try to email @BertrandBev , if he don't respond until Tuesday, I will create a fork and publish to pub.dev the fixes because I really need the read-only parameter.

mack-at-pieces commented 1 year ago

Hi @gumbarros @t-m-z @thekiwi - I understand the frustration here. I don't think it's required that you publish a new version of the package in order to use some of the features you're interested in.

What you can do is create a git dependency in your pubspec.yaml and point it to a specific commit, which you'll see is what I've done for my project below. This will give you access to the latest properties that I've also attached.

Screen Shot 2022-10-17 at 8 57 21 AM Screen Shot 2022-10-17 at 8 59 03 AM

Happy to help if you run into issues.

gumbarros commented 1 year ago

Hi @gumbarros @t-m-z @thekiwi - I understand the frustration here. I don't think it's required that you publish a new version of the package in order to use some of the features you're interested in.

What you can do is create a git dependency in your pubspec.yaml and point it to a specific commit, which you'll see is what I've done for my project below. This will give you access to the latest properties that I've also attached.

Screen Shot 2022-10-17 at 8 57 21 AM Screen Shot 2022-10-17 at 8 59 03 AM

Happy to help if you run into issues.

Genius, thanks!

BertrandBev commented 1 year ago

Hey @gumbarros & @thekiwi, Sorry for my lack of reactivity lately. I have a bunch on my plate, but I'll try to publish a new version sometimes tomorrow. In the meantime, @mack-at-pieces answer is definitely the way to go!