weird question #448
Replies: 3 comments 17 replies
-
|
Hi @KrzM, it really depends so much on what your needs and constraints are. It's not common for someone to use the console as their data entry point for the database, but it can make sense in some cases. If you use the console, making it intuitive for users is a lot of extra work, but maybe you don't need that if it's just for you. Using aspnet minimal apis can also be a low effort way to build an application to take data. It all depends on how you want to save and read the data. Have you tried asking questions on a site like stackoverflow? you can use tags like below and there are people who are giddy with excitement to offer help for this kind of stuff.
Reddit can be another good resource I'd recommend posting across a few sites and see which ones give you the most useful feedback. |
Beta Was this translation helpful? Give feedback.
-
|
Thx @drewburlingame |
Beta Was this translation helpful? Give feedback.
-
|
One thing I would suggest is that you start with as few abstractions as possible in your design. It's easy to overcomplicate it trying to follow a bunch of patterns that you don't end up needing. Although, it can be a good learning exercise to see how it fails. I'd recommend start with the bare minimum you need and then only add abstractions and extra layers when you need them. As a bare minimum, for something very fast, you could have a DTO representing the table in the DB. You could attribute the DTO with to use EF Core to save it to the DB. You could also make it an IArgumentModel and decorate the properties as arguments. Then your command is just saving the DTO to EF Core. You could create an abstract class with Save and Read commands for a DTO and then subclass that for each DTO. |
Beta Was this translation helpful? Give feedback.
-
|
I been toying with cli apps for at least tow moths now. |
Beta Was this translation helpful? Give feedback.
-
|
I suspect that looks insane |
Beta Was this translation helpful? Give feedback.
-
|
yeah, sometimes you've just got to try it to see what you think. Listen, if it works for you, it's the right choice for you. I think this would be more helpful if we had auto-complete for options, but we never finished that branch. If you often have multiple entries at once, another option is to use a CSV file to collect the data and a command to parse the csv file. Even more helpful if the data can be exported as CSV from another application. |
Beta Was this translation helpful? Give feedback.
-
|
I am chill testing to make sure it works before using runtime |
Beta Was this translation helpful? Give feedback.
-
|
If you've already created the console app, consider using https://commanddotnet.bilal-fazlani.com/testtools/harness/bdd/ to run the tests and that will exercise the entire console pipeline. It will be like running the app from the console. |
Beta Was this translation helpful? Give feedback.
-
|
I am doing my tests by runnig whole app in fixture |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
nice work. congratulations on your success. 🎉 |
Beta Was this translation helpful? Give feedback.
-
|
Now i try to remake it in to web apps becouse most jobs are in this |
Beta Was this translation helpful? Give feedback.
-
|
Hi @KrzM We talked a while back about how to make a simpler cli for CRUD operations. I saw you created a new one recently (it showed up as a in our list of github repos using CommandDotNet) and thought I'd throw together a quick suggestion on a way to structure the app that would be simpler, with less layers of indirection. With this app, you would just need an implementation of IRepository to register. You could use a tool like AutoMapper or Mapster to auto-map the IArgumentModels to the classes you save to the database. I think this will make your apps simpler to maintain and easier for others to grok when you get to the point of showing off your work. public class Program
{
public static void Main(string[] args)
{
IServiceProvider services = new ServiceCollection()
.AddSingleton<Crud<Album>>()
.AddSingleton<Crud<Song>>()
.BuildServiceProvider();
new AppRunner<Program>()
.UseNameCasing(Case.KebabCase)
.UseMicrosoftDependencyInjection(services)
.Run(args);
}
[Subcommand(RenameAs = "albums")]
public Crud<Album> Albums { get; set; }
[Subcommand(RenameAs = "songs")]
public Crud<Song> Songs { get; set; }
}
public class Crud<T> where T: IArgumentModel
{
private readonly IRepository<T> _repository;
public Crud(IRepository<T> repository) =>
_repository = repository ?? throw new ArgumentNullException(nameof(repository));
public void Create(IConsole console, T model)
{
console.WriteLine($"Creating {model}");
_repository.Add(model);
}
public void Update(IConsole console, T model)
{
console.WriteLine($"Updating {model}");
_repository.Update(model);
}
public void Delete(IConsole console, string name)
{
console.WriteLine($"Deleting {name}");
_repository.Delete(name);
}
public void Read(IConsole console, string name)
{
console.WriteLine(_repository.Get(name));
}
public void List(IConsole console)
{
foreach (var model in _repository.GetAll())
{
console.WriteLine(model);
}
}
}
public class Album : IArgumentModel
{
[Operand]
public string Name { get; set; }
public override string ToString()
{
return $"Album: {Name}";
}
}
public class Song : IArgumentModel
{
[Operand]
public string Album { get; set; }
[Operand]
public string Name { get; set; }
public override string ToString()
{
return $"Song: {Album} - {Name}";
}
}
public class IRepository<T>
{
public virtual IEnumerable<T> GetAll() => throw new NotImplementedException();
public virtual T Get(string id) => throw new NotImplementedException();
public virtual void Add(T entity) => throw new NotImplementedException();
public virtual void Update(T entity) => throw new NotImplementedException();
public virtual void Delete(string id) => throw new NotImplementedException();
}Hope this is helpful. Cheers, |
Beta Was this translation helpful? Give feedback.
-
|
Hi @KrzM, It's not about whether I like the structure or not. And it's not about whether you're a terrible coder. Please don't take my suggestion as judgement of your skill. I just remembered chatting before about layers of indirection. I didn't have time when we chatted back then to put together an example of what I was talking about, but had a few moments the other day so thought I'd offer it. I know you're still teaching yourself and thought it might be helpful to compare and contrast with what you have now. |
Beta Was this translation helpful? Give feedback.
-
|
Lets say i want to start new app. Simple notes taker. I want it to be simple as possible, but still plan ahead. First i need data layer. |
Beta Was this translation helpful? Give feedback.
-
|
This is certainly a common way to approach the problem, and if it's working for you, of course, there's nothing you need to change. You've built a framework to wrap other frameworks. That's not an uncommon approach. It has advantages and disadvantages. I was just offering an alternative that could possibly be interesting and requires less wrapping of CommandDotNet. It was interesting to me personally. I liked using the generic type for the Subcommand as a way to keep the code strongly typed while not redefining the command class. |
Beta Was this translation helpful? Give feedback.
-
|
I cant go into it right now. I am a little under the weather with severe runny nose. |
Beta Was this translation helpful? Give feedback.
-
|
I want a cli again. This time simple. No CRUD. So i will go with simplest template from your documentation page and it should be perfect. |
Beta Was this translation helpful? Give feedback.
-
Hi @drewburlingame
I have weird question, but you are only guy i have contact to, i can even ask it.
I want to have database with list/info on my stuff, things i own.
I think i will do single table ef core code first.
Then i will copy cli app templete i worked out, with commandDotNet.
This shuld take one day, with test and first data in.
It seems best bet to make it work for me.
Is there faster solution i am missing ?
I dont want plain sql or excel, it seems to be layer i can avoid.
Beta Was this translation helpful? Give feedback.
All reactions